From: Ian Campbell Date: Thu, 19 Dec 2013 10:08:39 +0000 (+0000) Subject: xen: arm: further clarify the requirement for cached mappings X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~5726 X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/success//%22http:/www.example.com/cgi/success/?a=commitdiff_plain;h=41fbf77bc87c79ae0b7dab2c47b8864c5dd34fb3;p=xen.git xen: arm: further clarify the requirement for cached mappings We need to include all shared memory, including grant table mappings etc in this statement. Signed-off-by: Ian Campbell Acked-by: Stefano Stabellini --- diff --git a/xen/include/public/arch-arm.h b/xen/include/public/arch-arm.h index ef6217d73e..2e7fb3e57c 100644 --- a/xen/include/public/arch-arm.h +++ b/xen/include/public/arch-arm.h @@ -59,10 +59,17 @@ * used regardless of guest type. Structures which are passed as * hypercall arguments are always little endian. * - * All hypercall arguments passed via a pointer to guest memory must - * reside in memory which is mapped as Normal Inner-cacheable. Any - * Inner cache allocation strategy (Write-Back, Write-Through etc) is - * acceptable. There is no restriction on the Outer-cacheability. + * All memory which is shared with other entities in the system + * (including the hypervisor and other guests) must reside in memory + * which is mapped as Normal Inner-cacheable. This applies to: + * - hypercall arguments passed via a pointer to guest memory. + * - memory shared via the grant table mechanism (including PV I/O + * rings etc). + * - memory shared with the hypervisor (struct shared_info, struct + * vcpu_info, the grant table, etc). + * + * Any Inner cache allocation strategy (Write-Back, Write-Through etc) + * is acceptable. There is no restriction on the Outer-cacheability. */ /*